-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lint upstream as a normal unit test #4918
Conversation
7cd6c4d
to
c2e930a
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4918 +/- ##
=======================================
Coverage 24.41% 24.41%
=======================================
Files 360 360
Lines 143270 143270
=======================================
Hits 34984 34984
Misses 108187 108187
Partials 99 99 ☔ View full report in Codecov by Sentry. |
@@ -493,9 +494,13 @@ var namespaceMap = map[string]string{ | |||
"aws": "Aws", | |||
} | |||
|
|||
var _nslock = sync.Mutex{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious what happened here, we ran awsMember call from multiple goroutines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's probably because of all the t.Parallel introduced into the tests? Interesting.
Assuming the upstream waf tests are unrelated. |
This PR has been shipped in release v6.66.0. |
This removes the last job in
extraTests
by making it a standard unit test.Currently the job runs without caching and takes upwards of 30-40 minutes because it re-compiles everything from scratch. This makes it the long poll when sharding is turned on.
By running with the rest of our tests it can benefit from caching. Locally the test takes only ~20s.
This is run during unit tests, which still take about ~5 minutes before and after this change. They're actually slightly faster because I parallelized some of them while I was in here.